From: Jorge Orpinel <jorge@orpinel.com>
To: git@vger.kernel.org
Subject: What are git subtree push assertions?
Date: Fri, 26 Sep 2014 17:24:51 -0400 [thread overview]
Message-ID: <CABf84+WFtO5rWHACk3cJagpKOnx2_USqWQ-vqtx+85fqEFbmzA@mail.gmail.com> (raw)
I asked this Q on
http://stackoverflow.com/questions/26068474/what-are-git-subtree-push-assertions
but from previous experiences with git-subtree, people on
stackoverflow (general public) don't really have complete answers so I
resort to you!
* What exactly are these assertions doing, and why does it have to
start from the beginning of the assertion count every time I subtree
push?
* Is there a way to limit the number of assertions? Something like git
subtree pull --squash perhaps. I don't want to wait this much or that
it'll break at some point when there's just too many.
Please refer to link above for full question details. Thanks in
advance for any info you can give.
Jorge O.
reply other threads:[~2014-09-26 21:25 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CABf84+WFtO5rWHACk3cJagpKOnx2_USqWQ-vqtx+85fqEFbmzA@mail.gmail.com \
--to=jorge@orpinel.com \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* 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.
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 NNTP newsgroup(s).