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

Re: [ANNOUNCE] chronoversion: chronological archiving script with temporary commits

From
Jakub Narebski <jnareb@gmail.com>
Date
Mar 13, 2007, 15:42 UTC
Message-ID
<et6gkk$ngm$1@sea.gmane.org>
In-Reply-To
<e1dab3980703130526t4b573f18h793a065d54c9369@mail.gmail.com>
[Cc: git@vger.kernel.org]
David Tweed wrote:
Show 5 quoted lines
> Hi, I believe that I've now got temporary commits (for bookkeeping,
> hi-granularity bisecting recent changes) working, so I'm just
> mentioning there's a new version of chronoversion at
> 
> http://www.personal.rdg.ac.uk/~sis05dst/chronoversion.tgz
By the way, do you have homepage for this project? If not, perhaps
you could write a few sentences on git wiki, e.g. at
  http://git.or.cz/gitwiki/Chronoversion
(linking it from http://git.or.cz/gitwiki/InterfacesFrontendsAndTools)
[...] 
> Is there any neat way of using builtin stuff like git-rev-parse to ask
> if a ref has a given SHA1 value and return an easily parsed yes/no
> answer?

There is git-show-ref which was made because of introduction of packed refs, and there is git-for-each-ref which _might_ be used to avoid extra forking (extra calls).

-- 
Jakub Narebski
Warsaw, Poland
ShadeHawk on #git
Previous: David TweedNext: Shawn O. Pearce
Message 2 of 5 in “[ANNOUNCE] chronoversion: chronological archiving script with temporary commits”
  1. David TweedMar 13, 2007
  2. Jakub NarebskiMar 13, 2007
  3. Shawn O. PearceMar 13, 2007
  4. Johannes SchindelinMar 13, 2007
  5. Johannes SchindelinMar 13, 2007

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.