git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Eugene Sajine <euguess@gmail.com>
To: Jakub Narebski <jnareb@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: gitweb - bare repos integration - owner info in description file
Date: Fri, 9 Oct 2009 18:32:25 -0400	[thread overview]
Message-ID: <76c5b8580910091532yd6c6fc4ib942a29c827f3a6c@mail.gmail.com> (raw)
In-Reply-To: <m3ab00gr25.fsf@localhost.localdomain>

>
> RTFM (in this case gitweb/README).  gitweb.owner and gitweb.description
> configuration variables in per-repository config.
>

Ok, my bad, didn't get there;)It is good to know there are places
where to keep the info. But it is not the point. The point is to
integrate gitweb with bare repo creation more than it is right now by
providing keys which will help filling out this info at the bare repo
creation stage.

shortly i'm talking about command like this (the key names are for sample only):

$ git clone --bare repo repo.git -desc "description" -gwowner
"gitwebowner@server.com" -cloneurl "git://host/repo.git"

seems to me quite comfy, and no headache...


> %
> "To be fair, there are uses for XML. On Halloween, for example."
>
>     - Johannes Schindelin, on git@vger.kernel.org
> %

yeah, to show kids xml print outs as an answer to "trick or treat!".
Can save on candies;)

Thanks,
Eugene

  reply	other threads:[~2009-10-09 22:34 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-09 20:50 gitweb - bare repos integration - owner info in description file Eugene Sajine
2009-10-09 22:07 ` Jakub Narebski
2009-10-09 22:32   ` Eugene Sajine [this message]
2009-10-10 18:45     ` Jakub Narebski
2009-10-11  1:45       ` Eugene Sajine
2009-10-11 10:39         ` Jakub Narebski
2009-10-12  0:04       ` Johannes Schindelin
2009-10-12 21:48         ` Eugene Sajine
2009-10-12 23:19           ` Miklos Vajna
2009-11-03 20:22           ` Petr Baudis
2009-11-04 23:48             ` Eugene Sajine

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=76c5b8580910091532yd6c6fc4ib942a29c827f3a6c@mail.gmail.com \
    --to=euguess@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=jnareb@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).