Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Duplicate code - 'dry run' did nothing #190

Closed
wants to merge 1 commit into from

Conversation

jesusbagpuss
Copy link
Contributor

Duplicate set of document update+commit/eprint regenerate, both inside and outside the 'if not dry-run' block (effectively meaning that 'dry-run' was also a wet-run...).

Duplicate set of documentupdate+commit/eprint regenerate, both inside and outside the 'if not dry-run' block (effectively meaning that 'dry-run' was also a wet-run...
@jesusbagpuss jesusbagpuss deleted the patch-4 branch January 20, 2014 15:05
@jesusbagpuss
Copy link
Contributor Author

Probably shouldn't include the 'email someone' stuff in the dry run either...

sebastfr pushed a commit that referenced this pull request Jan 20, 2014
@sebastfr
Copy link

Code on master and 3.3 now ok?

@jesusbagpuss
Copy link
Contributor Author

I think so - got my commits in a twist and couldn't seem to edit it (so I closed it and opened a new one)...

@sebastfr
Copy link

Laaaaame... I only saw the first pull request, which was closed as you
said... Well at least it's all committed now...

Seb.

On 20/01/14 17:09, jesusbagpuss wrote:

I think so - got my commits in a twist and couldn't seem to edit it
(so I closed it and opened a new one)...


Reply to this email directly or view it on GitHub
#190 (comment) Bug
from
https://github.com/notifications/beacon/912679__eyJzY29wZSI6Ik5ld3NpZXM6QmVhY29uIiwiZXhwaXJlcyI6MTcwNTc3MDU5MCwiZGF0YSI6eyJpZCI6MjM4NjcyNDh9fQ==--6edd350b5a3f3f23efdd70d1777a6c0140e7e43b.gif

@jesusbagpuss
Copy link
Contributor Author

So I'll close this #191 then!

@sebastfr
Copy link

On 20/01/14 17:15, jesusbagpuss wrote:

So I'll close this #191 #191
then!


Reply to this email directly or view it on GitHub
#190 (comment) Bug
from
https://github.com/notifications/beacon/912679__eyJzY29wZSI6Ik5ld3NpZXM6QmVhY29uIiwiZXhwaXJlcyI6MTcwNTc3MDk1OCwiZGF0YSI6eyJpZCI6MjM4NjcyNDh9fQ==--2d4b98f6b21cac38499b92cdf3fabf7a2d5becda.gif

Yes and I'll get all the glory for you fix, mwahaha!

@jesusbagpuss
Copy link
Contributor Author

👊
I'm thinking about making a 'pre-expiry-warning' rather than just a 'your embargo has expired' - I'll get the glory for that one :o)

@sebastfr
Copy link

On 20/01/14 17:31, jesusbagpuss wrote:

👊
I'm thinking about making a 'pre-expiry-warning' rather than just a
'your embargo has expired' - I'll get the glory for that one :o)


Reply to this email directly or view it on GitHub
#190 (comment) Bug
from
https://github.com/notifications/beacon/912679__eyJzY29wZSI6Ik5ld3NpZXM6QmVhY29uIiwiZXhwaXJlcyI6MTcwNTc3MTkxMywiZGF0YSI6eyJpZCI6MjM4NjcyNDh9fQ==--cdbe455a60e846349b72c804ce8edbecc6ed1761.gif

haha love the facepunch :-)

this sounds like an interesting feature, def something for the core!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants