From: spwhitton@spwhitton.name 
  
 control: retitle -1 git-debpush: --follow-tags passthrough option, escape 
 hatches, policy on passthrough options 
 control: severity -1 normal 
  
 Hello, 
  
 After IRC discussion this is what we think we will do: 
  
 - Add an escape hatch or hatches to pass arbitrary options to git-push 
   and git-tag ('git HERE tag HERE' and 'git HERE push HERE', so four 
   hatches). 
  
   + Note in docs that passing options to git-tag is especially 
     dangerous. 
  
   + Possibly also escape hatches for git-fetch. 
     We're not a wrapper for git-fetch in the same sense that we are for 
     git-tag and git-push, though. 
  
 - Add --follow-tags as a passthrough option, passed through to git-push. 
  
 - Document (in script header) and adopt policy that we generally highly 
   reticent to adopt new passthrough options, but will consider them if 
   they'll improve UX significantly for a broad enough group of users, as 
   opposed to requiring people to use the escape hatches. 
   These are some things that must be considered each time: 
  
   + If it's a passthrough option for one of git-tag or git-push, 
     consider whether there is already or might be in the future a 
     same-named option for the other command.  E.g. we've already a -u 
     passthrough option to git-tag but there is also a useful -u option 
     to git-push.  We don't want to do that again. 
  
   + Whether the name might be confusing in the context of tag2upload 
     (see below for an example). 
  
   + Whether the option is likely to cause chaos in this context. 
     E.g. we're unlikely to add --tags. 
  
   + Take into account the design principle that regular uploads 
     shouldn't require passing any options.  If this is an option someone 
     might always want to pass (contexts of scripting excepted), see if 
     we can find some other way to meet the use case. 
  
     (For --follow-tags if someone might always want to pass it they can 
     configure push.followTags in their global git config.) 
  
 - Don't add an option for git-push's --no-verify, at least not yet. 
   Write it in a comment in the script why: 
  
   + The name is not ideal and, specifically, could be confused with 
     an option changing something about how we make the tag. 
  
   + We could rename it to --no-git-pre-push-hooks or something but I 
     (Sean) think many people will find that more confusing (and indeed 
     offputting/annoying/too opinionated) than just having to use an 
     escape hatch option in order to pass it. 
  
   + We don't know how useful it is.  So wait for bug reports about 
     really wanting it. 
  
 -- 
 Sean Whitton 
  
 --=-=-Content-Type: application/pgp-signature; name="signature.asc" 
  
 -----BEGIN PGP SIGNATURE----- 
  
 iQJNBAEBCgA3FiEEm5FwB64DDjbk/CSLaVt65L8GYkAFAmigYXoZHHNwd2hpdHRv 
 bkBzcHdoaXR0b24ubmFtZQAKCRBpW3rkvwZiQK0XEACTNBSeJNP47UJUw/9aoMwU 
 cKN9zVgG+AxyDY5oGIb+Ru/GdzRXSHDCp6KOhH2h51dVHqLnjOnIFK5GMb4plOt4 
 uibxnuqNFsJ/5tloe2x200jfXfIA7M1jXfpn31YQrSeUpFROIIIaz2b/0B71iTOk 
 ptdcjbpSIgJ7BPiazohQB70ldF8K6PlGgQYQ603hZoN1qsDc+Rub8+1OCUN1CMpn 
 +Y90JvCtqke0kCeMUduc/oCmCL1bIz3b/HnKy7lhZiJdL0unkgTjF+rYByHcR6/f 
 2BzRl2ueh41IXxq/HluPFFf5Jv+Yh3ryn1INgl2iKjnWYCdwg1yzdeEV9ByMjswE 
 t9kQNgmqUTGGlE2TZg7jjs5VZzQ0TLag2aqCQv6+qqwLpFVDFHsrZ8FNPxKZ651X 
 CJ8+cgtswSm8KqEcrMM58Mf0VCpCrcaWZj74AWz29Z6Ka/kJnitUZ26aT0IR7JcD 
 41rH0lElvs+8DDi8O4l8+Xu+WjZkbS191+yFers132kHurx6/fTp4XkYq3vpwflV 
 P5hhefizK5w0hfrRFPoHFYcrt3NcXn+eUVZWaP9z5+XZAYic1Dh/DZKUJnnnzmoZ 
 i6izuRrD0dyW6XcKNB64t1bBxSl+ZrB1zq5dO04WwCYZDrWLU3CJhedVbAWkwd9m 
 dN+HytJLHy7/i3aG1RzD3A==2Nya 
 -----END PGP SIGNATURE----- 
  
 --- SoupGate-Win32 v1.05 
  * Origin: you cannot sedate... all the things you hate (1:229/2)