On Nov 26, 11:23 am, itroot ivan.tolstoshe...@gmail.com wrote:
Some branches in git are tracking another branches (for example,
usually master tracks origin/master). Let's assume, that in my work-
flow i don't want accidentally commit in master, but i want master to
track origin/master. I
On Fri, Nov 27, 2009 at 1:00 PM, Konstantin Khomoutov
khomou...@gmail.com wrote:
On Nov 26, 11:23 am, itroot ivan.tolstoshe...@gmail.com wrote:
Some branches in git are tracking another branches (for example,
usually master tracks origin/master). Let's assume, that in my work-
flow i don't
On Nov 27, 9:51 pm, Rick DeNatale rick.denat...@gmail.com wrote:
Some branches in git are tracking another branches (for example,
usually master tracks origin/master). Let's assume, that in my work-
flow i don't want accidentally commit in master, but i want master to
track origin/master. I
On Fri, Nov 27, 2009 at 1:58 PM, Konstantin Khomoutov
khomou...@gmail.com wrote:
On Nov 27, 9:51 pm, Rick DeNatale rick.denat...@gmail.com wrote:
Some branches in git are tracking another branches (for example,
usually master tracks origin/master). Let's assume, that in my work-
flow i don't
On Nov 27, 10:25 pm, Rick DeNatale rick.denat...@gmail.com wrote:
The concept for a fixed pointer to a commit is called a tag. If I
want to mark a point I might want to get back to, such as the commit
corresponding to a current release, the I tag it and push the tag.
Good point, but there's
