From: Markus Fischer <markus@fischer.name>
To: git@vger.kernel.org
Subject: Git bugtraq for all users who clone my repos?
Date: Mon, 28 Feb 2011 13:05:18 +0100 [thread overview]
Message-ID: <4D6B8F7E.4070804@fischer.name> (raw)
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
next reply other threads:[~2011-02-28 12:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-28 12:05 Markus Fischer [this message]
2011-02-28 13:14 ` Git bugtraq for all users who clone my repos? Sverre Rabbelier
2011-03-01 12:55 ` Pierre Habouzit
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4D6B8F7E.4070804@fischer.name \
--to=markus@fischer.name \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).