This is definitely front page material.
IngenieurLogiciel
@IngenieurLogiciel
Best posts made by IngenieurLogiciel
-
IGN gives Discourse 7.8/10 "Too much writing"
With the existing gaming mechanics (i.e. badges) and the potential for future ones (i.e. achievements, mini-games [e.g. buzzword bingo, speed FTFY]), I suggest submitting Discourse to Steam for Early Access (because it's obviously in alpha or beta, right?) and/or all the major gaming journalism outlets for publicity. This will help Discourse get off the ground as the first game in the new FPC (first person communication) genre.
As one who has lurked on the forums for the last two years, I really never thought of joining because Community Server wasn't fun. But now with Discourse, I have something to look forward to every day besides pushing buttons to make the pattern of lights change how I want. I, for one, will enjoy collecting all the badges I can and, hopefully, one day becoming the worst of the worst and joining TL4.
-
RE: Proving that Android’s, Java’s and Python’s sorting algorithm is broken (and showing how to fix it)
at java.util.TimSort.sort(TimSort.java:240)
I see the problem here. It was quite the poor design decision to have a sort only for Tims. What if I have an array of Bens or @accalias? Just goes to show how much of a Java is and has always been.
-
RE: *sigh* I guess if that's what you want...
abuse of both XML and CSV
And an abuse of Oracle tables. But I'm sure at least Oracle did something to deserve it.
-
RE: Request :frystare: emoji
ITT: Software developers try their hand at graphic design. The results are what you'd expect.
-
RE: Programming Language Learning Curves
Addendum:
4a. Log the errors and hide them from the user because they are only useful for debugging anyway.
-
RE: The Official Status Thread
When browsing with IE4, you have to ask yourself one question, "Do I feel lucky?" well, do you?
-
RE: Enlightened
At least it reads like proper English, instead of whatever @translator spewed sentences the EFL documentation is made out of.
-
RE: Because there's so much wrong with iTunes
Checkmate
My destiny was to post on this forum. All my years of training in being overly sensitive to semantics, details, and nuance have finally paid off.
Latest posts made by IngenieurLogiciel
-
RE: Poop Adobe Poop
only use PDFs
Except for when some corporate update screws the install up, and I can't read PDFs ever again.
-
RE: Git-style branch graphs
I was hoping for something simpler, I suck at git
This would give you a chance to learn without destroying anything important. </nothelping>
-
RE: Git-style branch graphs
Build an example repo with what could happen in theory, then use Git GUI, Eclipse's history tool, or your preferred history tool.
Also, Visio.
-
RE: Git/Atlassian Stash - how do combine commits before making a PR?
I don't know what that means. How do you get "prompted" with a text file?
When the CLI command is run, vi is initialized automatically with the text file to be edited.
... have I mentioned recently how many people tell me Git is a good high-quality tool? Christ.
I know that I'm not one of them. However, I do understand how it works even if it makes me want to find the developers would made it, especially the ones who wrote the docs, and slowly beat them to death with a spoon.
-
RE: Git/Atlassian Stash - how do combine commits before making a PR?
... ok? So you can do this on the remote branch?
What happens to the new set of commits? Do I just need to "push" them back to the remote, or do they need to go into a new branch or...?
On the branch you want to clean up commits:
$ git rebase -i HEAD~n
where n is the number of commits back in history, starting with the most recent (HEAD), you want to change. 2 would get you the top 2 commits, 3 would get you 3, etc.
It will prompt you with a commit message text file that you can edit which will tell the rebase command what to do with each commit.
Then do:
$ git push origin branchname --force
Note that lots of remotes reject forced pushes that rewrite history like this, because, as has been mentioned several times in this thread already, it is dangerous. For instance, if you did
$ git push --force 'Do not do this'
instead, it will rewind the histories of every local remote-tracking branch that you have, for which you haven't done a pull while on that branch recently. tmg;dr It deletes work.
The point of doing this is so the pull request is clean. Nobody would be pulling this branch until it's in pull request form.
You should be ok then. As long as you don't screw something up.
The StackOverflow link implies that opens a text file? Which I then edit somehow?
Isn't there just a GUI for this in some tool?
Yes, it opens a text file. Yes, if you are using the git Bash tool that installs as part of some git Windows installs, it comes up it in vi. You read that right, you are using vi in bash in Windows to edit git commits. No, there is no GUI for this that I know of.
-
RE: Git/Atlassian Stash - how do combine commits before making a PR?
Do you?
It's all lost for good, I get it, and I understand why you make so many commits. I'd do the same thing. But then I'm not as anal about making the commit history read like a novel like your boss, and would accept your workflow as is.
I did have an alternate solution, but...
Atlassian Stash doesn't allow that; every commit has to be attached to a Jira ticket. Even if it did, it doesn't solve the problem because:
I have no idea what that means or how to do it.
Reading about your constraints with git before, I was expecting as much. So I didn't put as much effort into making the alternate solution understandable as I should, because I didn't want to waste too much of your and my time with a solution you couldn't use anyway.