{"thread":{"id":"7017","subject":"[RFC] proposal for command \"publish\"","startedAt":"2007-02-28T13:49:43Z","lastAt":"2007-02-28T13:49:43Z","messageCount":1,"participants":["Paolo Bonzini"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"35803","messageId":"es419n$thr$1@sea.gmane.org","threadId":"7017","inReplyTo":null,"subject":"[RFC] proposal for command \"publish\"","fromName":"Paolo Bonzini","fromEmail":"bonzini@gnu.org","sentAt":"2007-02-28T13:49:43Z","receivedAt":"2007-02-28T13:49:43Z","isPatch":false,"sender":{"key":"bonzini@gnu.org","avatar":"https://avatars.githubusercontent.com/u/42082?v=4"},"body":"I'm proposing a command \"publish\", where\n\n   git publish URL\n\nwould do\n\n   git repack\n   git clone --bare . URL\n   git remote add origin URL\n\nThe idea is that this would be the step from preparing a repository \n(either from scratch, or importing from other SCM) to publishing it \nremotely.  Is this sensible?\n\nOptions from clone that would make sense for publish are -l, -q, \n--template, --upload-pack.\n\nPaolo\n"}]}