[aur-general] My AUR4 migration workflow

Florian Bruhin me at the-compiler.org
Fri Jun 12 04:46:15 UTC 2015

* Eli Schwartz <eschwartz93 at gmail.com> [2015-06-11 23:37:25 -0500]:
> On Thu, Jun 11, 2015 at 11:24 PM, Florian Bruhin <me at the-compiler.org>
> wrote:
> > Hmm. Instinctively I'd have agreed, but I can't reproduce this.
> >
> > I think git filter-branch actually checks out each "vanilla" commit
> > from the original branch to apply the given changes, and doesn't base
> > them on the already-changed commits:
> >
> > [...]
> >
> > Am I missing something? Have you actually verified this or is it just
> > a guess?  ;)
> >
> > [...]
> Either way, is it that terrible to make sure the .SRCINFO is up to date? If
> there is already one, it *should* just replace it with an identical copy...
> resulting in no diff. And if there is a diff, that means something once
> went wrong...

No, of course the change *does* make sense. Sorry for not making this
more clear in my answer.

I was mainly trying to figure out if I have to find out how I could
force-push to correct anything that's been pushed wrong, and then
found out it's hopefully not necessary to do so.


http://www.the-compiler.org | me at the-compiler.org (Mail/XMPP)
   GPG: 916E B0C8 FD55 A072 | http://the-compiler.org/pubkey.asc
         I love long mails! | http://email.is-not-s.ms/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <https://lists.archlinux.org/pipermail/aur-general/attachments/20150612/ec980edb/attachment.asc>

More information about the aur-general mailing list