> On Wed, Oct 25, 2023 at 02:15:43PM +0200, Uwe Brauer wrote: > [... I cut one piece from here to reply to it separately - see below ...]
> Well, the expanded explanation is exactly how I imagined it after reading your > initial mail, so I basically have nothing to add except minor clarifications. [Snip]... > Given that, there are two ways to make the changes available, and they are > basically the same: > - Just keep them outside of Git's control - that is, do not commit them > until there's time for them to get shared. > - Commit them, but do that on a separate branch. Whet it's time, you merge > that branch into the one used to share these changes, then push. I am an idiot (or more politely still have mercurial in mind, and forget that mercurial and git are in a lot of things orthogonal. In mercurial if you run hg push, you push all branches (if you want to push only the «current» branch you work on, you must specify this by adding an option, in git it is the other way around, git push, pushes only the actual branch if you want to push all branches, you need to add the relevant option) Ok, thanks for reminding me. Problem solved. -- Warning: Content may be disturbing to some audiences I strongly condemn Hamas terroristic attack on Israel, especially the despicable pogroms. I strongly condemn Putin's war of aggression against Ukraine. I support to deliver weapons to Ukraine's military. I support the NATO membership of Ukraine. I support the EU membership of Ukraine. https://addons.thunderbird.net/en-US/thunderbird/addon/gmail-conversation-view/ -- You received this message because you are subscribed to the Google Groups "Git for human beings" group. To unsubscribe from this group and stop receiving emails from it, send an email to git-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/git-users/87fs1xhq0d.fsf%40mat.ucm.es.
smime.p7s
Description: S/MIME cryptographic signature
