mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Junio C Hamano <>
To: Yuri <>
Cc: Johannes Sixt <>, Git Mailing List <>
Subject: Re: [feature suggestion] Add 'git stash export', 'git stash import' commands to allow to backup stash externally
Date: Thu, 06 May 2021 18:09:32 +0900	[thread overview]
Message-ID: <xmqqy2csxm7n.fsf@gitster.g> (raw)
In-Reply-To: <> ('s message of "Thu, 6 May 2021 01:41:13 -0700")

Yuri <> writes:

> On 5/6/21 1:38 AM, Junio C Hamano wrote:
>> Unlike centralized SCM like SVN and CVS, commits in Git are private
>> until you make them public by pushing, and you do not allow other
>> people to fetch/pull from the repository you actively work in.  If
>> your commits become public immediately after you make them, perhaps
>> there is a room in your workflow for vast improvement.
> Let's say I make commit1, commit2, commit3 and then commit4.
> How can I push only commit1 and commit3, but not commit2 and commit4?

You don't.

> Can I permanently hold some commits from being pushed while pushing others?

Yes, you arrange these unrelated things (e.g. if commit1 and commit3
can become ready to be used without commit2 and commit4, there is
*no* reason to build commit2 as a direct child of commit1 *AND*
build commit3 as a direct child of commit2) into multiple branches,
keep unrelated things separate and related things together, and push
the branch commit1 & commit3 are on (obviously in your example they
become ready to be consumed together while commit2 or commit4 are
not, so they wouldn't be on the same commit as commit2 or commit4).

  reply	other threads:[~2021-05-06  9:09 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-05 19:51 [feature suggestion] Add 'git stash export', 'git stash import' commands to allow to backup stash externally Yuri
2021-05-05 20:07 ` Randall S. Becker
2021-05-05 20:11   ` Yuri
2021-05-06  2:22   ` Junio C Hamano
2021-05-06  6:07 ` Johannes Sixt
2021-05-06  6:12   ` Yuri
2021-05-06  6:43     ` Johannes Sixt
2021-05-06  6:58       ` Yuri
2021-05-06  8:38         ` Junio C Hamano
2021-05-06  8:41           ` Yuri
2021-05-06  9:09             ` Junio C Hamano [this message]
2021-05-06 10:23             ` Felipe Contreras
2021-05-06  8:40         ` Felipe Contreras
2021-05-06  8:45           ` Yuri
2021-05-06 10:45             ` Felipe Contreras
2021-05-06 14:10             ` Theodore Ts'o

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

  List information:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=xmqqy2csxm7n.fsf@gitster.g \ \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).