also sprach Joey Hess [EMAIL PROTECTED] [2007.10.14.2359 +0100]:
I think it must be accidental that debcommit uses debian_version_ in
the name of git tags it creates. It does that for CVS because CVS has
limitations on tag names that require it not start with a number (IIRC).
But for svn and
martin f krafft wrote:
Please consider using debian/$version. Git does allow hierarchical
namespaces.
Would you say it's the most common/best choice for tag naming for git?
What about native packages, I don't think it makes much sense to put the
tags in debian/ for those.
I did think about
also sprach Joey Hess [EMAIL PROTECTED] [2007.10.17.1852 +0200]:
Would you say it's the most common/best choice for tag naming for git?
I'd say it's the one that makes most sense, yes. I don't know if
it's the most common.
What about native packages, I don't think it makes much sense to
put
martin f krafft wrote:
Why not? Someone else might actually clone our native packages into
a, say, Fedora repo, so we're keeping the namespace clean.
If they did, they'd likely consider debian the upstream. So it would
make sense for the tags to be upstream tags then.
--
see shy jo
also sprach Joey Hess [EMAIL PROTECTED] [2007.10.17.1944 +0200]:
If they did, they'd likely consider debian the upstream. So it would
make sense for the tags to be upstream tags then.
Fair point.
--
.''`. martin f. krafft [EMAIL PROTECTED]
: :' : proud Debian developer, author,
Package: devscripts
Version: 2.10.9
Severity: normal
I think it must be accidental that debcommit uses debian_version_ in
the name of git tags it creates. It does that for CVS because CVS has
limitations on tag names that require it not start with a number (IIRC).
But for svn and other vcses, it
6 matches
Mail list logo
