You can put a .gitconfig file in the repository but the user needs to manually include it in the local gitconfig http://stackoverflow.com/questions/18329621/storing-git-config-as-part-of-the-repository A script could be included as well to automate as much as possible the process of including it. Has the advantage at least of the config being with the repository and not stored separately on the server. //Derek -----Original Message----- From: Intel-gfx [mailto:intel-gfx-bounces@xxxxxxxxxxxxxxxxxxxxx] On Behalf Of Damien Lespiau Sent: Thursday, November 19, 2015 3:08 PM To: Jani Nikula Cc: intel-gfx@xxxxxxxxxxxxxxxxxxxxx Subject: Re: i-g-t/libdrm email tagging & patchwork On Thu, Nov 19, 2015 at 12:44:07PM +0200, Jani Nikula wrote: > On Wed, 18 Nov 2015, Daniel Vetter <daniel@xxxxxxxx> wrote: > > On Sun, Nov 08, 2015 at 12:31:36AM +0000, Damien Lespiau wrote: > >> Hi all, > >> > >> I've added a feature to sort the patches sent to intel-gfx into 3 > >> buckets: i915, intel-gpu-tools and libdrm. This sorting relies on > >> tagging patches, using the subject prefixes (which is what most > >> people do already anyway). > >> > >> - i915 (intel-gfx): catchall project, all mails not matching any of > >> the other 2 projects will end up there > >> > >> - intel-gpu-tools: mails need to be tagged with i-g-t, igt or > >> intel-gpu-tools > >> > >> - libdrm-intel: mails need to be tagged with libdrm > >> > >> This tagging can be set up per git repository with: > >> > >> $ git config format.subjectprefix "PATCH i-g-t" > > > > Is there any way we could push this out to users somehow? I have > > bazillion of machines, I'll get this wrong eventually ... So will > > everyone else I guess. > > Googling around, I don't think we can automatically force this on > people. We could add a script to make it easier for people to set this > up. Either a setup that needs to be re-run every time there are > changes, or a setup that symlinks a git hook back into a file stored > in the repository so changes are deployed automatically. The latter > has security implications, so I'd go for the former. So, we could have: $ git pw init https://patchwork.freedesktop.org/ intel-gpu-tools which would retrieve some server side config and shove it into .gitconfig. That does require a step anyway though, not sure how ideal this is or what else could be interesting to do with such a thing. -- Damien _______________________________________________ Intel-gfx mailing list Intel-gfx@xxxxxxxxxxxxxxxxxxxxx http://lists.freedesktop.org/mailman/listinfo/intel-gfx _______________________________________________ Intel-gfx mailing list Intel-gfx@xxxxxxxxxxxxxxxxxxxxx http://lists.freedesktop.org/mailman/listinfo/intel-gfx
