That is really nice! Thanks for the pointer.
--
You received this message because you are subscribed to the Google Groups "Git
for human beings" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to git-users+unsubscr...@googlegroups.com.
For more options, vi
On 14 February 2013 14:44, Fabrizio Cioni wrote:
> I'll have to accept the logic and to be very careful on my (and other) git
> behaviour, knowing when to be careful.
> I've studied and tested git for personal use in the last months, now that
> we're using in a group things get more interesting, a
My habit, when I am going to do something in a project is to:
cd ~/project
git branch
# more commands
just to remind me which branch is active immediately after I cd into the
subdirectory. I have some subdirectories which are "duplicated" on multiple
machines. The contents of each machine is in i
> From: Fabrizio Cioni
>
> I don't understand why the existing logic allows it, but i clearly see how
> a distracted/in a rush/sleepless developer can make a mess of it; still
> recoverable but very time-consuming when you find it x days later.
There is the converse problem of making a bunch o
Thanks Konstantin,
both for this answer and the linked one.
I'll have to accept the logic and to be very careful on my (and other) git
behaviour, knowing when to be careful.
I've studied and tested git for personal use in the last months, now that
we're using in a group things get more interestin
On Thu, 14 Feb 2013 01:02:29 -0800 (PST)
Fabrizio Cioni wrote:
> Example:
> 1) I'm working on branch "newfeatures" and i've edited some files
> 2) the customer call and warn me of a bug requiring a quick fix
> 3) i switch from "newfeatures" to "master" and i create a branch
> "fix_2000" from mast
