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

Re: What's cooking in git.git (topics)

From
Johannes Schindelin <johannes.schindelin@gmx.de>
Date
Jun 13, 2007, 22:44 UTC
Message-ID
<Pine.LNX.4.64.0706132334060.4059@racer.site>
In-Reply-To
<7vtztbbnsq.fsf@assigned-by-dhcp.pobox.com>
Hi,
On Wed, 13 Jun 2007, Junio C Hamano wrote:
> * js/filter (Fri Jun 8 23:28:50 2007 +0200) 11 commits

Isn't that convenient? That's already the second project the two JS'es are working together...

Show 7 quoted lines
> * jc/oneline (Mon Jun 11 22:10:55 2007 -0700) 2 commits
>  + Extend --pretty=oneline to cover the first paragraph,
>  + Lift 16kB limit of log message output
> 
> Hoping to be able to merge them to 'master', but haven't
> convinced myself that these changes are correct.  Help is
> appreciated.

I haven't had a chance to look at the patch yet, but the intention is sound.

Show 19 quoted lines
> * ei/worktree+filter (Wed Jun 6 09:16:56 2007 +0200)
>  - filter-branch: always export GIT_DIR if it is set
> * ml/worktree (Fri Jun 8 22:57:55 2007 +0200) 9 commits
>  - make git barf when an alias changes environment variables
>  - setup_git_directory: fix segfault if repository is found in cwd
>  - test GIT_WORK_TREE
>  - extend rev-parse test for --is-inside-work-tree
>  - Use new semantics of is_bare/inside_git_dir/inside_work_tree
>  - introduce GIT_WORK_TREE to specify the work tree
>  - test git rev-parse
>  - rev-parse: introduce --is-bare-repository
>  - rev-parse: document --is-inside-git-dir
> 
> Undecided.  Some people would want to have a way to have GIT_DIR
> point at somewhere unusual and still want to work from within a
> subdirectory, which is probably a valid thing to support.  This
> is not something I would use myself, so I am mostly worried
> about the impact these changes may have on people who do not use
> this feature.

Yeah, it is something to worry about. As far as I am concerned, these changes are too deep for too obscure a feature.

But then, I see that people need it.

And I can't think of a better way to implement it. So unless somebody comes up with a nice solution, I think we should live with it, rather than let it simmer in pu.

Ciao, Dscho

Previous: Junio C HamanoNext: Linus Torvalds
Message 21 of 34 in “What's cooking in git.git (topics)”
  1. Junio C HamanoMay 13, 2007
  2. Julian PhillipsMay 13, 2007
  3. Junio C HamanoMay 13, 2007
  4. Julian PhillipsMay 14, 2007
  5. Daniel BarkalowMay 14, 2007
  6. Junio C HamanoMay 17, 2007
  7. Daniel BarkalowMay 17, 2007
  8. Junio C HamanoMay 17, 2007
  9. Daniel BarkalowMay 17, 2007
  10. Junio C HamanoMay 19, 2007
  11. Junio C HamanoMay 23, 2007
  12. Shawn O. PearceMay 24, 2007
  13. Junio C HamanoMay 29, 2007
  14. Junio C HamanoJun 2, 2007
  15. Johannes SchindelinJun 3, 2007
  16. Shawn O. PearceJun 3, 2007
  17. Nicolas PitreJun 3, 2007
  18. Dana HowJun 3, 2007
  19. Junio C HamanoJun 7, 2007
  20. Junio C HamanoJun 13, 2007
  21. Johannes SchindelinJun 13, 2007
  22. Linus TorvaldsJun 14, 2007
  23. Matthias LederhoferJun 18, 2007
  24. Junio C HamanoJun 21, 2007
  25. Linus TorvaldsJun 21, 2007
  26. Linus TorvaldsJun 21, 2007
  27. Junio C HamanoJun 25, 2007
  28. Jeffrey C. OllieJun 25, 2007
  29. Matthias LederhoferJun 26, 2007
  30. Junio C HamanoJun 27, 2007
  31. Matthias LederhoferJun 28, 2007
  32. Junio C HamanoJun 29, 2007
  33. Junio C HamanoJul 2, 2007
  34. Junio C HamanoJul 28, 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.