From: Martin von Zweigbergk <martin.von.zweigbergk@gmail.com>
To: Kevin Sheedy <kevinsheedy@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Push to all repositories
Date: Thu, 9 Dec 2010 08:36:44 -0500 [thread overview]
Message-ID: <AANLkTik9CxVD9A-2QEyD_tZiyYoCOitfViWucGCudzh-@mail.gmail.com> (raw)
In-Reply-To: <1291898174244-5818757.post@n2.nabble.com>
On Thu, Dec 9, 2010 at 7:36 AM, Kevin Sheedy <kevinsheedy@gmail.com> wrote:
>
> In summary, I think it would be cool if there was a programmatic way of
> saying:
> "Hey everybody, I've changed some code on branch x and I think you should
> have it"
>
> Everyone else would then have the choices:
> 1) Always accept, I trust you (but don't blow away my current work,
> obviously)
I think the closest thing would be a cron job that runs "git pull"
every minute or so. A difference from dynamic views is that it would
no longer update your work tree once your changes start conflicting
with the upstream changes (in dynamic views, all unmodified files
would be updated).
However, rather than trying to make Git behave just like ClearCase
dynamic views (there are many other things to consider than automatic
updates), I think you would be better off if you actually use
ClearCase dynamic views instead.
> 2) Always ignore, I'll get it when I'm good and ready
This is of course the easy case; just run "git pull" manually.
/Martin
next prev parent reply other threads:[~2010-12-09 13:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-08 17:39 Push to all repositories Kevin Sheedy
2010-12-08 18:00 ` Jonathan Nieder
2010-12-08 22:59 ` Kevin Sheedy
2010-12-09 12:36 ` Kevin Sheedy
2010-12-09 12:47 ` Nguyen Thai Ngoc Duy
2010-12-09 13:36 ` Martin von Zweigbergk [this message]
2010-12-09 19:52 ` Jonathan Nieder
2011-01-02 9:54 ` Enrico Weigelt
2010-12-12 15:09 ` Enrico Weigelt
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=AANLkTik9CxVD9A-2QEyD_tZiyYoCOitfViWucGCudzh-@mail.gmail.com \
--to=martin.von.zweigbergk@gmail.com \
--cc=git@vger.kernel.org \
--cc=kevinsheedy@gmail.com \
/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).