kicad-developers team mailing list archive
-
kicad-developers team
-
Mailing list archive
-
Message #43305
Re: GitHub Mirror not updating?
-
To:
kicad-developers@xxxxxxxxxxxxxxxxxxx
-
From:
Wayne Stambaugh <stambaughw@xxxxxxxxx>
-
Date:
Mon, 20 Jan 2020 18:38:50 -0500
-
Autocrypt:
addr=stambaughw@xxxxxxxxx; prefer-encrypt=mutual; keydata= mQGiBEM0hxQRBAC2fNh3YOVLu1d5GZ0SbrTNldGiGnCJPLqzEnqFX9v6jmf33TMt6EmSLkl6 Wtfkoj0nVwKxcYmJkA8DX0QAokBkwNIzhSsBzQvthBLIk/5LnPVVKrEXOcL4mUyH1doKlkaE slgJozNa6Av+oavcvD02o1zJOloBbaHlNlyRt7fKswCgtIFlVjWggVH/15KfWk+Qo5JVPbME AIUBAQyL2OAx0n60AWec2WHnO9buHuG0ibtICgUMkE+2MRmYyKwYRdyVwGoIUemFuOyHp0AJ InX4T+vy2E7vkwODqjtMLfIoRkokW74Fi4nrvjlhOAw/vdq/twLbAmR9MOfPTpR4y7kQy1O2 /n+RkkRvh26vTzfbQmrH7cBJhk6aA/9Uwvu3E4zNJgHVZeS0HyWtmR1eOPPRbnkPgJTToX5O KMKzTJI/FX6kT7cFoCamitHrW3BJP4Dx+cMMsa47EGxqVTdbVJ4LjogsXTXxb+0Fn1u4zBdx x3Cer6O7+hqWy7zvpzeC6nSREjqDKa5CgHtv/GLm5uFPOmsjAsnHj2tlBrQmV2F5bmUgU3Rh bWJhdWdoIDxzdGFtYmF1Z2h3QGdtYWlsLmNvbT6IeAQTEQIAOBYhBOffs6CbblRzBkv33BtR cWlZ+CReBQJbFBS2AhsDBQsJCAcCBhUKCQgLAgQWAgMBAh4BAheAAAoJEBtRcWlZ+CReMI8A nRbrLkzp7+c2f0vX7sfg4ICX8LAKAJ9uClo4uJajmZa5zZrL2nKdZlUwIrkCDQRDNIcxEAgA gCru+3/aOC6RCjpvYC72wY+d5SmHphC6yeiV2/mOumyt5MLo/Ps2GznZr11JspqFk5K/Zpvp MMLqqjDZ39+50a2iKRQFJ6NlK+hJWMmj6eJygQrCwYo3Gjc6CqfrqUv+8VSnf/i5sIZmtOVA 4ZjML18MuBvMSsNdVLFJd5HNnYb1iOECpvqdPVh/21LLCEw7MUUGGnHBhCrmk2aJe5hFmcSN g4ldBcXrgMQBwf7aMVoobXBMFDb/IENByXn0llB7Gr2IFMRmNS9/p8s/II1Yl2bTqyX4FSz8 cfn7C9KEz7faZ7wzAcpwHFC/zs3JoAjJ0IEKdNUpIwAlKMzT3CzctwADBQf/cxpG28MKyrqk nNmq/8LQLy+x6FSYXBLjxQz9BiBNYeesDZQ6J5UbL1mjpJzMa5tLZypPYo4bbGyR22hrbyDF K7m6AcVaMIJKl98g4ukMutFfAJyRDaREH5Zl/X1P4u1Z/yaAIy9mKaNbaK1/5djNJ5wCTFen TUgAp9xdc30kGkFDdLJFp5uxDY4P0vaZiZdjUCvDM3Zjv5IzpNOfxVqTUBQNUP/BnnKhkk0p DTD6s3X8S+D0rOtEBQ8K0cwERI/E8EFa8nj0TNw4e2MYGR8wg+SxqJ7z5f0zPY0bO6G9DDFB wYCqzzPWGqdAh9vA5971TAbPERtdFybhkurozp2SfYhJBBgRAgAJBQJDNIcxAhsMAAoJEBtR cWlZ+CResHUAniULLCWiT26ieRTl7N2vS6vBo/DuAJ4m7Ss/gyiW6ybTn1ctDXAUgm2QVQ==
-
In-reply-to:
<CACp=VfZ7Q90tJ5M7rvGVG=BBmVEEYot37eeJRbGBW2WDzfisyQ@mail.gmail.com>
-
Openpgp:
preference=signencrypt
-
User-agent:
Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.9.0
Did someone already do this? I just checked the github repo and the
latest commit hash is correct.
On 1/20/20 5:46 PM, Ian McInerney wrote:
> The GitHub mirror will also need to be force pushed for its first
> update, since it looks like it got the first of the large files already
> mirrored to it and it was choking on the second of the files.
>
> -Ian
>
> On Mon, Jan 20, 2020 at 10:25 PM Simon Richter <Simon.Richter@xxxxxxxxxx
> <mailto:Simon.Richter@xxxxxxxxxx>> wrote:
>
> Hi Wayne,
>
> On 20.01.20 21:25, Wayne Stambaugh wrote:
>
> > If I run the commands Simon suggested to remove the blobs, what does
> > this mean for devs who pull from the dev repo on gitlab?
> After fetching normally, using
>
> $ git fetch
>
> anyone who doesn't have local work on top can just reset their
> branch, using
>
> $ git reset --keep origin/master
>
> to pivot over. The --keep option makes sure that no local changes are
> overwritten, and complains if it would do so.
>
> If they have local work, the sanest approach is to rebase on top of
> origin/master and delete the offending commits at the same time by doing
> an interactive rebase
>
> $ git rebase -i origin/master
>
> This gives a list of all commits that don't have identical content in
> the old and new history. Since the filtered branch is the same except
> for those four, the first four lines will be
>
> pick ea31730b4 Handle error returns from lstat.
> pick e83420f19 Remove file accidentally commited in ea31730b4
> pick e27e6ee16 Also catch null dereference in case wxASSERT was
> skipped.
> pick e1925b89c Remove file accidentally added in e27e6ee1
>
> and all local changes will follow those. You can either delete these
> lines from the todo list, or replace the work "pick" by "drop".
>
> The approach using "git filter-branch" is not recommended for normal
> developers, because it generates another alternate history that needs to
> be resolved by calling "git rebase origin/master", and when you're
> rebasing anyway, you can also remove the commits at that point.
>
> Wayne, if you want to avoid filter-branch, you can also use an
> interactive rebase:
>
> $ git rebase -i 9df2cfb32
>
> In the list, move the correction commits under the commits they fix, and
> replace "pick" by "fixup". The first six lines should read
>
> pick ea31730b4 Handle error returns from lstat.
> fixup e83420f19 Remove file accidentally commited in ea31730b4
> pick b3af41e1b RTree: Fix iterator in single branch trees
> pick e27e6ee16 Also catch null dereference in case wxASSERT was
> skipped.
> fixup e1925b89c Remove file accidentally added in e27e6ee1
> pick 7399465fd Handle nullptr.
>
> i.e. line 2 becomes "fixup", lines 5 and 6 are swapped, and line (now) 5
> also becomes "fixup".
>
> Both this method and the filter-branch method alter the committer name
> and date in the new history, so the commit IDs are not reproducible.
>
> Anyone but Wayne can of course run the same commands and get commits
> with identical contents but different ID, which a normal rebase will
> clean up nicely.
>
> The merge request workflow probably doesn't have to change (much), since
> we rebase changes before merging them, for these the same interactive
> rebase as above works.
>
> Simon
>
> _______________________________________________
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@xxxxxxxxxxxxxxxxxxx
> <mailto:kicad-developers@xxxxxxxxxxxxxxxxxxx>
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help : https://help.launchpad.net/ListHelp
>
>
> _______________________________________________
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help : https://help.launchpad.net/ListHelp
>
Follow ups
References