Git development
 help / color / mirror / Atom feed
From: "Björn Steinbrink" <B.Steinbrink@gmx.de>
To: Christian Jaeger <christian@jaeger.mine.nu>
Cc: Jens Neuhalfen <JensNeuhalfen@gmx.de>, git@vger.kernel.org
Subject: Re: SeLinux integration
Date: Mon, 18 Aug 2008 15:04:54 +0200	[thread overview]
Message-ID: <20080818130454.GA908@atjola.homenet> (raw)
In-Reply-To: <48A96F51.6090404@jaeger.mine.nu>

On 2008.08.18 14:47:13 +0200, Christian Jaeger wrote:
> Jens Neuhalfen wrote:
>> The repository is my current development repository which, naturally
>> (?), is based on the 'blessed' repository. My understanding of git
>> was, that anyone with a copy of the blessed git repository can 'pull'
>> from my repository and gets my branches with git transmitting just my
>> changes over the net. Then he/she/it can switch to 'my' branch and
>> test the policy/init-script.
>>
>> Did I get something wrong there? I thought that this is a/the normal 
>> way of using git.   
>
> Well I'm sure you could use it this way; but check for yourself, if you  
> start gitk on your repository, one has to first figure out where to find  
> you work, i.e. one has to follow the right parent in your commits to see  
> all of them; it's certainly possible but I guess not very inviting for  
> people who just want to *look* at your work (as opposed to simply try it  
> out). I'll readily admit that I just wanted to look, not try it out. But  
> maybe I'm not the only one with this as his/her primary aim.

Well, instead of using --reference, I would just add a "selinux" remote
to my existing git.git repo, fetch the stuff and then:

gitk origin/master..selinux/master

It's still not "pretty", but quite usable. And as far as I'm concerned,
it's kinda obvious that the git-selinux repo is based on the git.git
repo, so I wouldn't say that you're required to mention that explicitly.

Björn

  reply	other threads:[~2008-08-18 13:06 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-17 10:44 SeLinux integration Jens Neuhalfen
2008-08-18  8:45 ` Christian Jaeger
2008-08-18 12:02   ` Jens Neuhalfen
2008-08-18 12:47     ` Christian Jaeger
2008-08-18 13:04       ` Björn Steinbrink [this message]
2008-08-18 13:32 ` Petr Baudis
2008-08-18 14:29 ` David P. Quigley

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=20080818130454.GA908@atjola.homenet \
    --to=b.steinbrink@gmx.de \
    --cc=JensNeuhalfen@gmx.de \
    --cc=christian@jaeger.mine.nu \
    --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