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

Re: [PATCH] [1/2many] - FInd the maintainer(s) for a patch - scripts/get_maintainer.pl

From
RHRene Herman <rene.herman@gmail.com>
Date
Aug 16, 2007, 11:08 UTC
Message-ID
<46C43015.7080804@gmail.com>
In-Reply-To
<46C42DCB.1060502@gmail.com>
On 08/16/2007 12:58 PM, Rene Herman wrote:
> On 08/15/2007 03:52 PM, Kyle Moffett wrote:
Show 33 quoted lines
>> If you were going to do that I'd just suggest making git aware of the 
>> "user.*" extended attributes and having it save those into the git 
>> repo along with the permission data.
> 
> Am looking at it but am not so sure that's a very good idea. I guess 
> it'd be largely okay-ish to require the repo to be on a filesystem that 
> supports EAs for this feature to work, but keeping the attributes intact 
> over file system operations seems not all that easy (yet). Having not 
> used EAs before I may be missing something but my version of "cp" for 
> example (GNU coreutils 6.9) appears to not copy them. Nor do they seem 
> to survive a trip through GNU tar 1.16.1. EAs appear to not be very 
> useful unless every single tool supports them -- a repo should be 
> resistant against simple operations like that.
> 
> Googling around, I see subversion already has this and calls the 
> meta-data "properties" (svn propset/get and friends). It uses a few 
> properties itself, such as the svn:executable property (which I saw is 
> also the only permission bit git keeps) and svn:ignore, which serves the 
> same role as the .gitignore files for git. Both those would fit into 
> this scheme nicely for git as well, if git were to do something similar 
> and reserve for example the "git.*" namespace for internal use.
> 
> Junio (and others), do you have an opinion on this? If these properties 
> are versioned themselves such as in svn I believe it's a decidedly 
> non-trivial addition (and I'm a complete git newbie) but to me, they 
> look incredibly useful, both for the original "maintainers" properties 
> (and anyone else one would want to come up with such as summary 
> properties and author/license stuff) and even for git internal reasons 
> such as sketched above.
> 
> The git-blame thing as sketched before by Linus would never be able to 
> point out mailing lists, or general lists of "interested parties" for 
> example, but these properties can do anything...

The svn implemention is that a single property is free-form text. As such, I guess a property would be just another file, although one that only lives in the index and is linked from the file/directory it is a property of.

Perhaps that immediately suggests an implementation to someone already familiar with git internals?

Rene.
Previous: Rene HermanNext: Salikh Zakirov
Message 14 of 38 in “Re: [PATCH] [1/2many] - FInd the maintainer(s) for a patch - scripts/get_maintainer.pl”
  1. Joe PerchesAug 14, 2007
  2. Rene HermanAug 14, 2007
  3. Joe PerchesAug 14, 2007
  4. Rene HermanAug 14, 2007
  5. Linus TorvaldsAug 14, 2007
  6. Joe PerchesAug 14, 2007
  7. Al ViroAug 14, 2007
  8. Joe PerchesAug 14, 2007
  9. Rene HermanAug 15, 2007
  10. Satyam SharmaAug 15, 2007
  11. Rene HermanAug 15, 2007
  12. Kyle MoffettAug 15, 2007
  13. Rene HermanAug 16, 2007
  14. Rene HermanAug 16, 2007
  15. Salikh ZakirovAug 16, 2007
  16. Rene HermanAug 16, 2007
  17. Al ViroAug 16, 2007
  18. Rene HermanAug 16, 2007
  19. Junio C HamanoAug 16, 2007
  20. Rene HermanAug 17, 2007
  21. Krzysztof HalasaAug 15, 2007
  22. Al ViroAug 15, 2007
  23. Richard KnutssonAug 15, 2007
  24. Stefan RichterAug 15, 2007
  25. Ray LeeAug 15, 2007
  26. Joe PerchesAug 16, 2007
  27. Junio C HamanoAug 15, 2007
  28. Joe PerchesAug 15, 2007
  29. Junio C HamanoAug 15, 2007
  30. Rene HermanAug 15, 2007
  31. Stefan RichterAug 15, 2007
  32. Rene HermanAug 15, 2007
  33. Joe PerchesAug 15, 2007
  34. Joe PerchesAug 17, 2007
  35. Joe PerchesAug 17, 2007
  36. - git-send-email.perlJoe Perches, Aug 17, 2007
  37. Junio C HamanoAug 17, 2007
  38. Joe PerchesAug 18, 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.