git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Steffen Prohaska <prohaska@zib.de>
Cc: Marius Storm-Olsen <marius@trolltech.com>,
	Git Mailing List <git@vger.kernel.org>,
	"Shawn O. Pearce" <spearce@spearce.org>
Subject: Re: msysgit: does git gui work?
Date: Fri, 10 Aug 2007 14:53:54 +0100 (BST)	[thread overview]
Message-ID: <Pine.LNX.4.64.0708101452060.21857@racer.site> (raw)
In-Reply-To: <31EFF30A-CC7A-4BB0-B083-13A1F7B62781@zib.de>

Hi,

On Fri, 10 Aug 2007, Steffen Prohaska wrote:

> On Aug 10, 2007, at 2:13 PM, Johannes Schindelin wrote:
> 
> > On Fri, 10 Aug 2007, Steffen Prohaska wrote:
> > 
> > > On Aug 10, 2007, at 12:16 PM, Johannes Schindelin wrote:
> > > 
> > > > On Fri, 10 Aug 2007, Steffen Prohaska wrote:
> > > 
> > > I agree and pushed the following to mob
> > > 
> > > faeb4e3df9fb7c853dd1a46d6942776d4a743545
> > > 
> > > I forced a non-fast-forward of mob. Is this ok? Apparently it's allowed.
> > 
> > Yes, it is allowed exactly for this purpose.  When you want to redo/undo
> > commits.
> > 
> > > Another question related to mob. How do I need to setup /git/.git/config
> > > to be able to push to git's mob?
> > 
> > My understanding is that the GitMe installer already sets up a remote
> > named "mob".
> > 
> > 	$ git push mob
> > 
> > It automatically pushes the "master" branch to "mob".  If you have to
> > force the push, you'll have to do this:
> > 
> > 	$ git push mob +master:mob
> > 
> > But please avoid this when possible, since you might well overwrite other
> > people's work.
> 
> I have a mob for /.git, but I do not have the setup for /git/.git. Maybe
> I deleted it because I didn't understand what is means.

Ah, I misunderstood.  Yes, it is quite possible to have a mob installed 
for 4msysgit.git by default.  Should by done in 
msysgit.git:share/GitMe/setup-msysgit.sh.

> Whoever has setup the mob configurations, maybe it would be a good idea 
> to forbid non-fast-forward but instead allow the creation of new mob* 
> branches. If I can't push to mob, I could push to mob-topic instead. 
> Cleanup would be in the responsibility of the repository owner.

This is not possible.  The refusal of a non-fast-forward is a per-repo, 
not a per-user, configuration.

Ciao,
Dscho

  reply	other threads:[~2007-08-10 13:54 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-09  7:24 msysgit: does git gui work? Steffen Prohaska
2007-08-09 21:23 ` Steffen Prohaska
2007-08-10  5:31   ` Shawn O. Pearce
2007-08-10  7:03     ` Steffen Prohaska
2007-08-10  7:38       ` Steffen Prohaska
2007-08-10  7:47         ` Marius Storm-Olsen
2007-08-10 10:26           ` Steffen Prohaska
2007-08-10 10:16       ` Johannes Schindelin
2007-08-10 10:51         ` Steffen Prohaska
2007-08-10 12:13           ` Johannes Schindelin
2007-08-10 13:48             ` Steffen Prohaska
2007-08-10 13:53               ` Johannes Schindelin [this message]
2007-08-10 16:47                 ` Steffen Prohaska
2007-08-10 11:40         ` Alex Riesen
2007-08-11  6:10           ` Dmitry Kakurin
2007-08-11  8:40             ` Alex Riesen
  -- strict thread matches above, loose matches on Subject: below --
2007-08-10 22:00 Brett Schwarz

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=Pine.LNX.4.64.0708101452060.21857@racer.site \
    --to=johannes.schindelin@gmx.de \
    --cc=git@vger.kernel.org \
    --cc=marius@trolltech.com \
    --cc=prohaska@zib.de \
    --cc=spearce@spearce.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).