git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Getting a branch's time of creation

From
Jjateeq <jawad_atiq@hotmail.com>
Date
Mar 17, 2010, 17:24 UTC
Message-ID
<1268846646146-4751743.post@n2.nabble.com>
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.
Previous: Randal L. SchwartzNext: Jakub Narebski
Message 3 of 4 in “Getting a branch's time of creation”
  1. jateeqMar 17, 2010
  2. Randal L. SchwartzMar 17, 2010
  3. jateeqMar 17, 2010
  4. Jakub NarebskiMar 19, 2010

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.