On Tuesday, July 3, 2012 7:17:29 AM UTC+2, jack sparrow wrote:
> On Jul 3, 9:51 am, PJ Weisberg <pjweisb...@gmail.com> wrote:
> > On Monday, July 2, 2012, jack sparrow <dafs...@gmail.com> wrote:
> > > From the git repo, i created a new branch1 with the existing tag tag1.
> > > i made some changes to a set of files, filea, fileb. If i run git
> > > status
> > > it shows that the filea and fileb are modified, so far good. Now i
> > > created
> > > another branch2 with the existing tag tag2. If i go toa filea, the
> > > file has
> > > the changes i made in the branch1. since the changes i made are
> > > commited,
> > > i was expecting the file to be without the modfications that was made
> > > in
> > > other branch. am i missing something ?
> > Maybe, but it's hard to say without knowing specifically what commands
> > ran.
> > --
> > -PJ
> > Gehm's Corollary to Clark's Law: Any technology distinguishable from
> > magic is insufficiently advanced.
> git clone remote-repo
> git tag
> git checkout -b tag1 tag1
> vi filea
> vi fileb
> make changes to filea fileb
> git checkout -b tag2 tag2
> vi filea - here i still see the changes made in branch tag1
> i was hoping the file to be having the same contents
> as in the tag2, excluding the un committed changes
> from tag1
> i hope i am little bit clear.
As we discussed recently in another thread, Git moves any local changes
along during checkout:
By the way, it's probably a bad idea giving your branches the same names as
your tags. If you have a tag for the release version 1.5, and you want a to
base a branch on it, it's better to call it something like 1.5.x, to better
express the "movement" in the branch.
You received this message because you are subscribed to the Google Groups "Git
for human beings" group.
To view this discussion on the web visit
To post to this group, send email to firstname.lastname@example.org.
To unsubscribe from this group, send email to
For more options, visit this group at