Re: Standardizing the layout of git packaging repositories
On Tue, 19 Aug 2014, Lars Wirzenius wrote:
> On Mon, Aug 18, 2014 at 07:28:51PM -0400, Barry Warsaw wrote:
> > Also, it makes me somewhat uncomfortable to assume that a git tag in the
> > upstream repo will always be equivalent to their released tarball. In fact,
> > it's often not, as is the case with Python packages containing a MANIFEST.in.
>
> I would even be uncomfortable assuming that an upstream tag never
> moves to point at a different commit. (Been there, seen that.)
So have I. And git didn't warn about it at the time, either. It just
ignored the changed [remote] tag and kept the one it already had. Maybe it
will raise a ruckus nowadays, but I'd not bet on that.
FWIW, I always git-import-orig and _then_ git diff it to the upstream remote
branch. All upstream branches are set to fast-forward-only mode, as well.
--
"One disk to rule them all, One disk to find them. One disk to bring
them all and in the darkness grind them. In the Land of Redmond
where the shadows lie." -- The Silicon Valley Tarot
Henrique Holschuh
Reply to: