git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: jateeq <jawad_atiq@hotmail.com>
To: git@vger.kernel.org
Subject: Re: Getting a branch's time of creation
Date: Wed, 17 Mar 2010 09:24:06 -0800 (PST)	[thread overview]
Message-ID: <1268846646146-4751743.post@n2.nabble.com> (raw)
In-Reply-To: <86wrxakiyj.fsf@blue.stonehenge.com>


Great, that works -  it gives me the commit that Branch 1 was at at the time
of cloning.

One concern however. If I clone the repository, create Branch 2 to track
Branch 1, and in the mean while push changes to the master branch of the
repository, the commit that this command gives me changes (to the last
commit that was pushed). The repository I am cloning from is bare, so in
order to make changes to the master, I clone it again, make changes to the
master branch of the clone and push those back (of course, this clone also
has Branch 1 as a remote branch, but I am not making changes to it). What is
git doing? Why does it change the commit history of Branch 1 when I did not
push changes to it? 

Before pushing to master:
$git log --oneline $(git merge-base origin/jateeq.2010-03-16.15-32
origin/master)..origin/master
610cfae added file.xml

After pushing to master:
$git log --oneline $(git merge-base origin/jateeq.2010-03-16.15-32
origin/master)..origin/master
9070a4d removed fcc.xml


Thanks, 
Jawad
-- 
View this message in context: http://n2.nabble.com/Getting-a-branch-s-time-of-creation-tp4750687p4751743.html
Sent from the git mailing list archive at Nabble.com.

  reply	other threads:[~2010-03-17 17:24 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-17 14:45 Getting a branch's time of creation jateeq
2010-03-17 16:32 ` Randal L. Schwartz
2010-03-17 17:24   ` jateeq [this message]
2010-03-19 20:54 ` Jakub Narebski

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1268846646146-4751743.post@n2.nabble.com \
    --to=jawad_atiq@hotmail.com \
    --cc=git@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).