threads / discuss / 26619

Git bugtraq for all users who clone my repos?

Subject: Git bugtraq for all users who clone my repos?

## tl;dr

3 messages between Feb 28, 2011 and Mar 1, 2011.

replies: 2people: 3as markdown or json

Markus Fischer· Feb 28, 2011, 12:05 UTC · lore

Hi,

I'm used to svn to use svn:propset to set bugtraq URLs, pus^H^H^Hcommit them to the server and all users who clo^H^H^Hcheckout from it have the settings.

In git I can store them in my local or repository specific configuration, but other users who clone from it don't benefit from it: they simply don't get my/the bugtraq configuration.

Do I need to educate every developer to configure their checkouts (also unsatisfying for myself when I move somewhere else have to do clone my repository again) or it possible to feed it when the repository is being cloned?

thanks,
- Markus

Sverre Rabbelier· Feb 28, 2011, 13:14 UTC · re: Markus Fischer · lore

Re: Git bugtraq for all users who clone my repos?

Heya,

On Mon, Feb 28, 2011 at 13:05, Markus Fischer <markus@fischer.name> wrote:

> Do I need to educate every developer to configure their checkouts (also
> unsatisfying for myself when I move somewhere else have to do clone my
> repository again) or it possible to feed it when the repository is being
> cloned?

Perhaps 'git notes' is what you're looking for?

-- 
Cheers,

Sverre Rabbelier

Pierre Habouzit· Mar 1, 2011, 12:55 UTC · re: Markus Fischer · lore

Re: Git bugtraq for all users who clone my repos?

On Mon, Feb 28, 2011 at 01:05:18PM +0100, Markus Fischer wrote:

Show 14 quoted lines

> Hi,
> 
> I'm used to svn to use svn:propset to set bugtraq URLs,
> pus^H^H^Hcommit them to the server and all users who
> clo^H^H^Hcheckout from it have the settings.
> 
> In git I can store them in my local or repository specific
> configuration, but other users who clone from it don't benefit from
> it: they simply don't get my/the bugtraq configuration.
> 
> Do I need to educate every developer to configure their checkouts
> (also unsatisfying for myself when I move somewhere else have to do
> clone my repository again) or it possible to feed it when the
> repository is being cloned?

This is horrible practice, but the top level makefile / configure of some of my projects force the git configuration of the repository to some sane values that are required for it to work properly.

-- 
·O·  Pierre Habouzit
··O                                                madcoder@debian.org
OOO                                                http://www.madism.org