git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Shawn O. Pearce" <spearce@spearce.org>
To: Robin Rosenberg <robin.rosenberg.lists@dewire.com>
Cc: Nigel Magnay <nigel.magnay@gmail.com>, Git ML <git@vger.kernel.org>
Subject: Re: [PATCH JGIT] Minor : Make ObjectId, RemoteConfig Serializable
Date: Sun, 8 Feb 2009 11:47:45 -0800	[thread overview]
Message-ID: <20090208194745.GA30949@spearce.org> (raw)
In-Reply-To: <200902082045.22703.robin.rosenberg.lists@dewire.com>

Robin Rosenberg <robin.rosenberg.lists@dewire.com> wrote:
> söndag 08 februari 2009 20:10:24 skrev Shawn O. Pearce:
> > In the case of any of the types you are discussing there is an easy
> > canonical form for them to be written on the wire, or to read back:
> > 
> >   ObjectId     - the 20 byte SHA-1
> >   RefSpec      - the string form as it appears in the config file
> >   URIish       - the string form as it appears in the config file
>
> with our without the password?

With.

We're serializing the object, we should store as much of the data
as we have.  Clients throwing this over the wire should either be
careful with their connection (e.g. use SSL) or be careful with
the data they are throwing (e.g. don't use URIish that has password).
 
-- 
Shawn.

      reply	other threads:[~2009-02-08 19:49 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <320075ff0902060702n7573aaecu9054626ee9a6991@mail.gmail.com>
2009-02-06 21:15 ` [PATCH JGIT] Minor : Make ObjectId, RemoteConfig Serializable Nigel Magnay
2009-02-08  2:13   ` Robin Rosenberg
2009-02-08 13:26     ` Nigel Magnay
2009-02-08 19:10       ` Shawn O. Pearce
2009-02-08 19:45         ` Robin Rosenberg
2009-02-08 19:47           ` Shawn O. Pearce [this message]

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=20090208194745.GA30949@spearce.org \
    --to=spearce@spearce.org \
    --cc=git@vger.kernel.org \
    --cc=nigel.magnay@gmail.com \
    --cc=robin.rosenberg.lists@dewire.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).