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

Re: post-fetch, tweak-fetch hook

From
MMitar <mmitar@gmail.com>
Date
May 6, 2012, 23:54 UTC
Message-ID
<CAKLmikNYewaRL3DUG9+NvpH3Y6sf=oJVdOo2DQSDw4vKH+Km-Q@mail.gmail.com>
In-Reply-To
<201205062310.q46NAHnM022630@no.baka.org>
Hi!
Thank you for examples. They guide me in good direction. But still ...
On Mon, May 7, 2012 at 1:10 AM, Seth Robertson <in-gitvger@baka.org> wrote:
> I'm in favor of more git hooks myself, but there is a solution to your
> needs without it.

Of course there is a solution. Bash is turing-complete programming language. But the question is how easy and fast it is to use something.

> If you care about race conditions (and really, a lockfile(1) call can
> take care of that easily enough),

If git would support post-fetch hook, I would get this for free and would not have to care about race conditions.

> then parse the output of fetch which will make it clear what *this* call did.

Yes, because it is really easy to parse it? There are so many different things it can output and I am not sure how to find which one should I take care of and which one should I ignore. Yes, I could learn much more about git and all possible things which can happen with fetch and its output, but I am trying to avoid this. Why? Because I believe it should be much easier.

I am sorry if I look a bit negative, but I am quite frustrated that for something so simple is so hard (in a time/knowledge meaning) to achieve. Of course there is a way and that if you know all git command this is maybe obvious, but why it couldn't be easier, if it is really a very simple patch to make it easier (and it was already posted to this mailing list few months ago).

Mitar
Previous: Seth RobertsonNext: Jeff King
Message 3 of 6 in “post-fetch, tweak-fetch hook”
  1. MitarMay 6, 2012
  2. Seth RobertsonMay 6, 2012
  3. MitarMay 6, 2012
  4. Jeff KingMay 7, 2012
  5. MitarMay 7, 2012
  6. Jeff KingMay 7, 2012

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.