Eric Kow wrote: > On 6 Aug 2012, at 21:19, Ben Franksen <[email protected]> wrote: >> Miles Gould wrote: >>> I for one would be confused by a "send" command that doesn't send >>> anything - both when trying to figure out the behaviour of "darcs send" >>> and when trying to work out which command I need to create a patch file. >> >> +1 from my side. A send command that doesn't send anything is just >> confusing. Why not try to send and if it fails for whatever reason create >> the patch bundle as a file (and say so)? > > Mmm, sorry. I didn't do a very good job making the context behind this > change clear. The issue is that as things stand we don't even know if > things fail. It just silently does the wrong thing > > The proposed send reminds you that it didn't actually send the patch and > tells you how to set darcs up so that it does. The wording needs a bit of > work though
Well, that's bad for sure, but why not try to improve that? I can't believe there is no way to find out if sending an email failed. > The proposed send reminds you that it didn't actually send the patch and > tells you how to set darcs up so that it does. The wording needs a bit of > work though Wording changes or no, I would always expect 'darcs send' to really send something, or at least try. Why not make a new 'darcs create-patch-bundle' command? -- Ben Franksen () ascii ribbon campaign - against html e-mail /\ www.asciiribbon.org - against proprietary attachments _______________________________________________ darcs-users mailing list [email protected] http://lists.osuosl.org/mailman/listinfo/darcs-users
