Skip to content

Conversation

@saschastahl
Copy link
Contributor

No description provided.

@alexpearce
Copy link
Member

This is much nicer. We could just update the instructions to use these commands. Best to specify only one way, particularly if there's one that's objectively better.

@saschastahl
Copy link
Contributor Author

You mean just remove the other bullet point?

@gdujany
Copy link
Member

gdujany commented May 24, 2016

mmm, not sure it is objectively better in all cases. I would claim that the first option is better If I have to checkout packages from different projects, especially if I intend to run locally some tests to see if the rebase did not break anything.

@alexpearce
Copy link
Member

OK, then we should expand on this. It's important to be clear; I do git pull loads in non-LHCb projects, so it would be great to provide instructions how this works for LHCb.

@gdujany
Copy link
Member

gdujany commented May 24, 2016

well, for my understanding now there is not a simple git lb-pull or a git lb-fetch but hopefully they will be there in the future so I guess it is fine to keep the links to the twiki in a challenge section now and hopefully update the section with simpler commands soon

@saschastahl
Copy link
Contributor Author

I think you have to repeat git lb-use to pull upstream changes.

@apuignav
Copy link

apuignav commented Apr 28, 2017

Hi guys, do we have an update on this? What should we do with this PR?

@alexpearce
Copy link
Member

There's still no way to effectively rebase an lb-dev project, so I think this is still relevant.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants