Christian Welzel wrote:
> Would it be an option to use tags instead of commit ids? As i read
> git can tag any object, so you can tag the commit (or tree) after import
> and use that. filter-tree at least warns abount not changing tags if
> someone changes the commit.
As long as a tag continues to
Am 12.03.2012 03:03, schrieb Joey Hess:
> pristine-tar commit writes, to the pristine-tar branch of your
> repository, a file named `$origtarball.id`. This file contains the
> git sha1 of the branch you told it to commit, which is the data
> that pristine-tar checkout relies on to put the tarbal
Christian Welzel wrote:
> Hi there,
>
> i ran into this problem today.
> I modified my repo by filter-branch to set the committer-date
> to the author-date, and then ran git gc. Now pristine-tar cannot
> export the tar.gz anymore:
>
> (master)$ pristine-tar -vd checkout typo3-src_4.5.11+dfsg1.ori
Hi there,
i ran into this problem today.
I modified my repo by filter-branch to set the committer-date
to the author-date, and then ran git gc. Now pristine-tar cannot
export the tar.gz anymore:
(master)$ pristine-tar -vd checkout typo3-src_4.5.11+dfsg1.orig.tar.gz
pristine-tar: git archive --for
4 matches
Mail list logo