On Sun, Jun 04, 2017 at 11:35:46PM +0100, Richard W.M. Jones wrote: > On Sun, Jun 04, 2017 at 07:24:36PM +0200, Pierre-Yves Chibon wrote: > > On Sun, Jun 04, 2017 at 02:42:20PM +0100, Tom Hughes wrote: > > > On 04/06/17 14:22, Richard W.M. Jones wrote: > > > > > > > > Sorry to push on this some more, but I'm still unclear on the details. > > > > > > > > Will the second Pagure instance store exploded trees of the upstream > > > > software? Will the dist-git RPM source + patches form be generated > > > > from that? > > > > > > As I understand it the repos will remain the same, there will just be a new > > > web interface in front of them, and pkgdb will go away and instead you will > > > be able to grant people push access in the pagure interface. > > > > That is correct, nothing is changing on the disk side but instead of the cgit > > interface we will have pagure on the top of the repo, allowing the use the > > fork/pull-request workflow. > > But we're still going to be able to use plain git, right? > Anything that requires a non-command-line interface for ordinary > procedures would be a step backwards IMHO. Plain git still usable the same ways, yes. The things Pagure is doing are additive (fork/PR, CI hooks, etc.). -- Paul W. Frields http://paul.frields.org/ gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717 http://redhat.com/ - - - - http://pfrields.fedorapeople.org/ The open source story continues to grow: http://opensource.com _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
