git clone --depth=1 and git reset --hard; git push -f? #2

New issue

Closed

opened 2015-12-05 23:28:55 +01:00 by ghost · 2 comments

ghost commented

2015-12-05 23:28:55 +01:00

(Migrated from github.com)

Hi,

This is a huge repository coming from Bitcoin initially. Are you planning to cherry pick things from upstream Bitcoin/BitcoinXT? If so, does having the commit history help?

I wonder if it would be worth it to reset the repo to the state where you started modifying it for lbrycrd. Would really shrink it down, possibly with no side-effects (maybe something legally?).

This is very minor and nitpicky, but I'm also curious of a good reason not to, because it could be something I've not though of and should know.

Thanks,
Teran

Hi, This is a huge repository coming from Bitcoin initially. Are you planning to cherry pick things from upstream Bitcoin/BitcoinXT? If so, does having the commit history help? I wonder if it would be worth it to reset the repo to the state where you started modifying it for lbrycrd. Would really shrink it down, possibly with no side-effects (maybe something legally?). This is very minor and nitpicky, but I'm also curious of a good reason not to, because it could be something I've not though of and should know. Thanks, Teran

whitslack commented

2016-03-16 04:08:53 +01:00

(Migrated from github.com)

@teran-mckinney There's no reason to erase history from the repository on GitHub, and keeping the history allows automated merging from upstream. If you don't want to download the full history when checking out lbryio/lbrycrd, you can do a shallow clone.

ghost commented

2016-03-16 16:22:19 +01:00

(Migrated from github.com)

That's fair, I think you're right.

Thanks!

That's fair, I think you're right. Thanks!

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: LBRYCommunity/lbrycrd#2

No description provided.