On Mon, Jun 01, 2009 at 09:09:48PM +0300, Fabian Fagerholm wrote:
If this is the consensus, should then Vcs-Browser point to trunk also?
Without having given it too much thought, I would suggest not. Instead
point it at the root of the repository.
Why? Vcs-* are meant to be in sync, with
On Tue, 2009-06-02 at 09:13 +0200, Stefano Zacchiroli wrote:
Why? Vcs-* are meant to be in sync, with -Browser being the
human-friendly facet to inspect what is in the repo. I fail to see why
it should point elsewhere.
[...]
I think you are considering a svn-biased point of view. The notion of
Recently I've ran into a few cases were doing debcheckout of a package using
svn downloads the whole thing: tags, branches and trunk. I would expect
debcheckout to give me just the HEAD of development. What should be the sane
behavior?
--
Felipe Sateler
--
To UNSUBSCRIBE, email to
On Mon, Jun 1, 2009 at 2:04 PM, Felipe Sateler fsate...@gmail.com wrote:
Recently I've ran into a few cases were doing debcheckout of a package using
svn downloads the whole thing: tags, branches and trunk. I would expect
debcheckout to give me just the HEAD of development. What should be the
On Mon, Jun 01, 2009 at 04:04:48PM +1000, Felipe Sateler wrote:
Recently I've ran into a few cases were doing debcheckout of a package using
svn downloads the whole thing: tags, branches and trunk. I would expect
debcheckout to give me just the HEAD of development. What should be the sane
On Mon, 2009-06-01 at 08:18 +0200, Stefano Zacchiroli wrote:
Should be somewhere where you can natually invoke a package build
command. Ideally, and for $VCS that contain injected upstream sources,
it should be the root of a debianized source tree, i.e. `pwd` should
contain debian/.
For
6 matches
Mail list logo
