On Friday, May 8, 2015 at 11:53:02 AM UTC+2, Thomas Ferris Nicolaisen wrote:
If you still can justify why this would be a valuable feature for a
noteworthy amount of Git users, the place to suggest new features is the
main Git mailing list: https://gist.github.com/tfnico/4441562
Please
Michael keybou...@gmail.com writes:
Lets say you've got files set up to commit to one point in the tree,
but you're actually in a different location. How do you move where you
are / where a commit will go, without altering the files?
git reset --soft branch
looks like the command that does
On Sunday, May 10, 2015 at 2:14:36 AM UTC+2, Tricia Finkle wrote:
Hi,
I'm just getting started with github and git. I have tried to download
git several times from the git-smc site, source forge and mirror sites. I
install it and it says install successful, but then it is nowhere to be
On 9 May 2015 11:59 pm, Michael keybou...@gmail.com wrote:
So here's something that I'd like to do, and I'm wondering if Git is the
right tool for this.
I have a program's config file, that is broken up into a large number of
sections. One of them is causing a problem. All of them have been
Last question for tonight
Lets say you've got files set up to commit to one point in the tree, but
you're actually in a different location. How do you move where you are /
where a commit will go, without altering the files?
keybounceMBP:Loot++ michael$ git stash
Saved working directory
Lets say you've got files set up to commit to one point in the tree, but you're
actually in a different location. How do you move where you are / where a
commit will go, without altering the files?
How did I get here?
714 git checkout 4194
715 git tag -a baseChest -m Branch here for
On 2015-05-09, at 11:03 PM, Michael keybou...@gmail.com wrote:
Lets say you've got files set up to commit to one point in the tree, but
you're actually in a different location. How do you move where you are /
where a commit will go, without altering the files?
Alright, what happened here?
Hello,
how about using stash?
git add -p (or use git gui) to add some lines you want to check, but don't
commit
git stash --keep-index
do your tests. If everything is fine, make a commit
git stash pop
start over
when you are finished, you will have several commits, so you may want to
squash
Keep index?
-u?
(reads manual)
...
(reads git-clean)
...
Definitely do NOT want -u :-).
Git stash gives me the same issue, unless there is something I don't know
about. In order to do the test, the checked out working copy needs to NOT have
spare/untested chunks in it.
In other words, I have
